Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1124

reference: 679-tree-1
name: 1124
tree-preservation-order: undefined
679-tpo-1
uprn
address-text
point: POINT (-1.017694 50.879947)
geometry: MULTIPOLYGON (((-1.017652 50.879943,-1.017653 50.879951,-1.017659 50.879958,-1.017669 50.879965,-1.017694 50.879970,-1.017707 50.879969,-1.017719 50.879965,-1.017728 50.879959,-1.017735 50.879952,-1.017737 50.879943,-1.017735 50.879935,-1.017729 50.879927,-1.017720 50.879921,-1.017708 50.879917,-1.017695 50.879916,-1.017682 50.879917,-1.017670 50.879921,-1.017660 50.879927,-1.017654 50.879934,-1.017652 50.879943)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL